Expected Differences

• Do these changes introduce new tools, command line arguments, or configuration file options? [Yes or No]
  
  If yes, please describe:
  

Yes. This PR brings in a new make file (SRC/FEMAIN/Makefile.hip) that can be used to build FastEddy for AMD GPU accelerated platforms. I've also included a small bit of documentation for building FastEddy on AMD GPU systems, using this new make file. These changes do not require any modification to source code in main_v2.0, as the instructions provided in Makefile.hip leverage ROCm's hipify-clang to convert CUDA code to HIP code prior to compilation with amdclang++/hipcc.

Pull Request Testing

• Describe testing already performed for these changes:
  

I've run the convective boundary layer example on both Nvidia V100 and AMD MI210 systems. @jsauer-NCAR has reviewed model output from both runs and confirmed solutions are in agreement.

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  
  Reviewers are invited to obtain an account on our system to test FastEddy on AMD MI210 GPUs, should they want to run existing tutorials on the AMD platform. Please reach out to me directly to get an account.

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes or No]

Yes. However, I could imagine it being worthwhile to include docs on how to run on systems with AMD GPUs (in addition to the build instructions). To this end, we can provide run instructions for our cluster (Galapagos). I might be able to request cycles on Setonix to put together run instructions on Pawsey Supercomputing Centre's Setonix. Down the road, if users or maintainers wish to run on Frontier, we'd be happy to join in on an allocation request for Frontier and help develop build and run documentation specifically for Frontier.

• Do these changes include sufficient testing updates? [Yes or No]
  No. This is only due to the lack of availability of CI platforms that offer AMD GPUs for testing. Fluid Numerics' Galapagos cluster could do this, but we would need to discuss a support contract to provide GPU-hours dedicated for CI connected via Github Actions and our superci tool.

• Will this PR result in changes to the test suite? [Yes or No]
  
  If yes, describe the new output and/or changes to the existing output:
  

Not presently.

• Please complete this pull request review by January 28, 2025.
  

Pull Request Checklist

• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Select: Reviewer(s)
• After submitting the PR, select the ⚙️ icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.